Android SDK tools revision 12 has problem with Proguard => error conversion to Dalvik format failed with error 1?

The problem is caused by ProGuard command line in R12 in the file Android SDK Installation Directory\tools\proguard\bin\proguard.bat. Simply edit the following line will solve the problem Change call %java_exe% -jar "%PROGUARD_HOME%"\lib\proguard. Jar % to call %java_exe% -jar "%PROGUARD_HOME%"\lib\proguard.

Jar %1 %2 %3 %4 %5 %6 %7 %8 %9.

The problem is caused by ProGuard command line in R12 in the file Android SDK Installation Directory\tools\proguard\bin\proguard.bat. Simply edit the following line will solve the problem. Change call %java_exe% -jar "%PROGUARD_HOME%"\lib\proguard.

Jar %* to call %java_exe% -jar "%PROGUARD_HOME%"\lib\proguard. Jar %1 %2 %3 %4 %5 %6 %7 %8 %9.

I can confirm that this change does fix the problem. – Yongki Jul 11 at 15:23 If it doesn't work, setup the environment variable (PROGUARD_HOME) manually in "Advanced System Settings" for your computer/user. In my case, my path had a space but it was working in R11.

– Ernest Laurentin Jul 19 at 7:58 Thank you! I have had this problem for a while... – Prem N. Jul 28 at 18:05 I'm surprised that this broke... :( But your change works... Thanks!

– Jona Aug 9 at 19:38 Thank you so much! This actually does work and AT LAST solved the problem for me... No idea WTF this answer is not marked as accepted :( – Alexander O Aug 20 at 19:52.

I downloaded Proguard 4.6 and copied the contents of /lib and /bin into /tools/proguard/ which fixed the problem.

This is the proper way to resolve this issue. CLeaning, reverting to an earlier sdk, etc. Are all incorrect (the may work for some in certain cases, but the proper way to resolve this issue is to download Proguard 4.6 as stated by Michiel) – Lysogen Sep 30 at 15:05.

I just fixed this issue by downloading the the R11 installer from dl.google.com/android/installer_r11-wind... and replacing the \tools directory with this one: Run the downloaded installer. Specify a different destination folder than the regular install and click through to Install. At then end you can uncheck "Start SDK Manager...", and click Finish.

The installer will create a \tools directory in that different folder. Rename your regular "\android-sdk-windows\tools" directory, and copy that \tools directory to your regular "\android-sdk-windows\" directory. The project should now build without the "Error 1".

I haven't looked into what is different in the 2 directories yet.

I have the same problem and I can confirm that I don't get the error by replacing the R12 Proguard folder with the R11 one. – BrainCrash Jul 10 at 11:46 Simply overwriting proguard folder solved the problem but it somehow causes the emulator to crash with message: "PANIC: Missing arch-specific emulator program: C:\Android_Devs\android-sdk-windows-1.5_r3\tools/emulator-arm. Exe" – Yongki Jul 10 at 18:39.

The only solution i've found to this problem is to change, in proguard. Cfg -optimizationpasses 5 to -optimizationpasses 2.

Changing proguard. Bat as suggested didn't help in my case. Upgrading to proguard 4.6 also didn't help.

What helped me is that I had to downgrade to Android SDK tools to revision 11. Note: when running SDK Manager and installing packages, I didn't install package "Android SDK Tools, revision 12". UPDATE: I have tried with Android SDK revision 15, but the issue is still present.

Now this workaround of downgrading to revision 11 does not work any more, as URL that SDK Manager is using to download packages is not working any more. After 2 days of trying different solutions, upgrading to proguard 4.6 did help.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.